-
Notifications
You must be signed in to change notification settings - Fork 188
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix inconsistent env var naming for LDAP filter configuration #3898
Conversation
💥 Acceptance test localApiTests-apiAccountsHashDifficulty-ocis failed. Further test are cancelled... |
@micbar should we make this backwards compatible? |
I would prefer to have this change mentioned prominently in the release notes for the next beta. If we keep this backwards compatible there would be four different envvars to configure the same setting in the |
yes, we need it in the release notes. I would like to have also a note in the changelog what needs to be done for an existing deployment. |
@mmattel JFYI |
Inform @pmaier1 in time as he does the RN writing. |
There was a naming inconsitency for the enviroment variables used to define LDAP filters for user and groups queries. Some services used `LDAP_USER_FILTER` while others used `LDAP_USERFILTER`. This is now changed to use `LDAP_USER_FILTER` and `LDAP_GROUP_FILTER` Closes: owncloud#3890
Makes sense. I've added a Note. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
There was a naming inconsitency for the enviroment variables used to define
LDAP filters for user and groups queries. Some services used
LDAP_USER_FILTER
while others used
LDAP_USERFILTER
. This is now changed to useLDAP_USER_FILTER
and
LDAP_GROUP_FILTER
Closes: #3890